<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Business Analyst Community &amp; Resources | Modern Analyst</title> 
        <link>https://modernanalyst.com</link> 
        <description>RSS feeds for Business Analyst Community &amp; Resources | Modern Analyst</description> 
        <ttl>60</ttl> <item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2776/Taking-Quality-for-Granted.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2776</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2776&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Taking Quality for Granted</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2776/Taking-Quality-for-Granted.aspx</link> 
    <description>&amp;nbsp;Quality must be built into the product during design, not inspected in afterwards.&amp;nbsp;Beyond the mechanics of quality though, people must learn to care about the work products they are charged to produce. &amp;nbsp;Quality requires both discipline and a conscientious work force. You cannot have one without the other.
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Sun, 14 Jan 2024 08:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2776</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6042/Change-Requests-for-Software-Business-Analysts.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6042</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6042&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Change Requests for Software Business Analysts</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6042/Change-Requests-for-Software-Business-Analysts.aspx</link> 
    <description>A change request (CR) is basically any change in the initial set of signed-off requirements. So, typically in a waterfall model implementation, the requirements phase ensures that all the requirements (features/functionalities/functional and non-functional) are agreed upon and documented before development starts. After that, any new scope brought or requested by clients becomes a change request. There is an additional cost associated with implementing a change request.

Even in the agile model of working, although there is flexibility in the implementation of the project, vendors ensure that a high-level set of requirements are discussed and agreed upon. The iterative way of working ensures that clients have their eyes on the product as it is developing and can suggest corrections or alignments. However, no vendor can work with entirely flexible requirements. It&amp;#39;s not feasible from a budgeting standpoint.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 27 Mar 2022 22:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6042</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5931/Design-Demands-Iteration.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5931</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5931&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Design Demands Iteration</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5931/Design-Demands-Iteration.aspx</link> 
    <description>There&amp;rsquo;s always more than one design solution for a software problem and seldom a single best solution. The first design approach you conceive won&amp;rsquo;t be the best option. As one experienced designer explained it:

You haven&amp;rsquo;t done your design job if you haven&amp;rsquo;t thought of at least three solutions, discarded all of them because they weren&amp;rsquo;t good enough, and then combined the best parts of all of them into a superior fourth solution. Sometimes, after considering three options, you realize that you don&amp;rsquo;t really understand the problem.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 03 Oct 2021 07:26:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5931</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5724/Recommendations-For-Updating-The-BABOK.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5724</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5724&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Recommendations For Updating The BABOK</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5724/Recommendations-For-Updating-The-BABOK.aspx</link> 
    <description>These are my findings from analyzing the Business Analysis Body Of Knowledge, version 3 (BABOK). These findings are presented in the form of, suggestions for improvement, potential errors and omissions. They are the result of creating an object-oriented model of the structure and information of the BABOK. This model captures 461 pages of the BABOK - from the Business Analysis Key Concepts chapter through to the end of the Techniques To Tasks Mapping chapter.
</description> 
    <dc:creator>lmunday</dc:creator> 
    <pubDate>Sun, 15 Nov 2020 19:13:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5724</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5651/You-have-to-be-mature-to-be-agile.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5651</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5651&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>You have to be mature to be agile</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5651/You-have-to-be-mature-to-be-agile.aspx</link> 
    <description>An agile organization is characterized by having a comprehensive portfolio of optimized business process and business capability maps grouped by their role in value creation for the customers and support of the business strategy.&amp;nbsp; These maps are linked to all the other disciplines such as finance, governance, resource management, talent management, and customer experience.&amp;nbsp;&amp;nbsp; Thus, Corporate IP can be securely delivered to the point of need.&amp;nbsp;
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 19 Jul 2020 16:24:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5651</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5625/66-Lessons-from-50-Years-of-Software-Experience.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5625</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5625&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>66 Lessons from 50 Years of Software Experience</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5625/66-Lessons-from-50-Years-of-Software-Experience.aspx</link> 
    <description>I spent a lot of time in the past half-century doing software work: requirements, design, user experience, programming, testing, project management, writing documentation, process improvement leadership, writing 7 books and many articles, consulting, and training.&amp;nbsp;Sure, there were some side trips along the way,.... But basically I&amp;rsquo;m a software guy.&amp;nbsp;Over all that time, I&amp;rsquo;ve accumulated numerous insights about the software business. Here I offer 66 of those lessons. Perhaps you&amp;rsquo;ll find them as helpful as I have.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 12 Jul 2020 06:06:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5625</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5617/Design-Thinking-in-a-Waterfall-World.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5617</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5617&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Design Thinking in a Waterfall World</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5617/Design-Thinking-in-a-Waterfall-World.aspx</link> 
    <description>As much as we like to think we are now in a dynamic and agile world, most delivery initiatives are still some shades of agile and all shades of waterfall.&amp;nbsp;These initiatives could have adopted an agile outlook and naming convention, but the businesses they support are often still predominantly waterfall &amp;ndash; going from one clearly defined task to another until realizing value. Think for example, order to cash, just in time logistics etc.</description> 
    <dc:creator>oluwakorede</dc:creator> 
    <pubDate>Sun, 21 Jun 2020 13:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5617</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5604/A-Practical-Guide-to-Transition-from-Waterfall-to-Agile.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5604</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5604&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>A Practical Guide to Transition from Waterfall to Agile</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5604/A-Practical-Guide-to-Transition-from-Waterfall-to-Agile.aspx</link> 
    <description>The transition from Waterfall to Agile is never easy &amp;ndash; especially for a business analyst who must go through this journey. This document has come about because of this challenge and as an attempt to present a practical guide of how to effectively transition over as a business analyst, and where are these worlds connected. I do not believe that all that we learned as business analyst in the waterfall era are completely useless. What has changed in the Agile world is how we think about analysis, how we present the requirements to our business and our development and testing teams. It is by no means a comprehensive and one size fits all document. But it does provide a start and a guide for those who sometimes cannot make the connection.
Using one fictitious&amp;nbsp; &amp;lsquo;User Story&amp;rsquo; in the Agile section of this document, I provide concrete examples of how and when to present just enough information, while giving your audience sufficient understanding of what they need to bring the requirements to life.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Tue, 26 May 2020 02:44:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5604</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5462/Whats-Missing-from-Agile.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5462</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5462&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What’s Missing from Agile?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5462/Whats-Missing-from-Agile.aspx</link> 
    <description>John Seddon launches an attack on the value of Agile as practiced and charts a better way to analyse and design for improvement, making information technology the last thing to be concerned with, not the first.</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 20 Oct 2019 18:48:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5462</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5401/How-BAs-Fit-into-Projects-and-Development.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5401</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5401&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How BAs Fit into Projects and Development</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5401/How-BAs-Fit-into-Projects-and-Development.aspx</link> 
    <description>As the business analyst (BA) role continues to evolve, the responsibilities continue to expand. One of the best ways for a business analyst to add value to a project is to understand the processes involved in both the project life cycle (PLC) and the software development life cycle (SDLC). Contrary to popular belief, the two life cycles are&amp;nbsp;independent&amp;nbsp;of one another, however, it&#39;s best that they are aligned.</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 29 Jul 2019 08:11:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5401</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5357/Ninety-Percent-Done.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5357</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5357&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Ninety Percent Done</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5357/Ninety-Percent-Done.aspx</link> 
    <description>The fact that software projects and tasks are reported to be &amp;ldquo;90 percent done&amp;rdquo; for a long time has become something of an industry joke. (A related joke states that the first half of a software project consumes the first 90 percent of the resources, and the second half consumes the other 90 percent of the resources.) This well-intentioned but misleading status tracking makes it difficult to judge when a body of work will truly be completed so you can ship the next product release to your customers. Here are several typical causes of &amp;ldquo;90 percent done&amp;rdquo; syndrome and a few possible cures.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 22 Jul 2019 00:33:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5357</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5315/The-Core-Question-about-Building-Better-Software.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5315</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5315&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Core Question about Building Better Software</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5315/The-Core-Question-about-Building-Better-Software.aspx</link> 
    <description>In recent years, agile software development has been the classic example of this pursuit of magic solutions, so I&amp;rsquo;ll use that as an example here. Over the years, though, people have leapt onto the bandwagons of numerous new software approaches. They all have merits, they all have limitations, and they all need to be applied to appropriate problems.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 14 Apr 2019 08:39:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5315</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5083/Lets-explore-Business-Analysts-Toolbox.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5083</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5083&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Let&#39;s explore Business Analysts&#39; Toolbox</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5083/Lets-explore-Business-Analysts-Toolbox.aspx</link> 
    <description>Chaos! Stress! Everyday mess! Isn&amp;rsquo;t this an everyday situation for a business analyst? If not, either you&amp;rsquo;ve job satisfaction or you&amp;rsquo;re not being introduced to the real world of business analysis.
A person might possess great skills, however, (s)he might not be able to utilize skills without the right mix of tools and environment. A toolbox enables a person to implement the skills in the most efficient way. Possessing necessary tools is just the one part of it. Another is the knowledge to utilize the right tools at the right time to cater the solution and ensure timely committed delivery.
What are these tools? How do we map the usage of tools to the given circumstance? How can we efficiently utilize the tool? Does it depend on the solution or the approach?</description> 
    <dc:creator>Nimil Parikh</dc:creator> 
    <pubDate>Sun, 08 Jul 2018 12:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5083</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3740/The-State-of-IT-in-Business.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3740</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3740&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The State of I.T. in Business</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3740/The-State-of-IT-in-Business.aspx</link> 
    <description>Watching the speed by which Information Technology (I.T.) has changed over the last forty years has been amazing. Hardly a day goes by without some new twist or invention. In particular, my interest is in how I.T. can be applied to support the systems needed to operate a business, such as for manufacturing, inventory, order processing, customer service, accounting, human resources, and much more. I have seen a lot during the last four decades, perhaps too much.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 23 Mar 2017 18:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3740</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3507/Business-Analyst-vs-Superman.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3507</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3507&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Business Analyst vs. Superman</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3507/Business-Analyst-vs-Superman.aspx</link> 
    <description>Since when were Business Analysts a one stop shop for all project needs? We are expected to be Superheros; well-rounded BAs as well as Change Managers, Test Analysts, Project Managers and Implementation Managers. The boundaries of these other disciplines is often unclear so this article seeks to explore the activities that fall into business analysis and those that should be undertaken within the other disciplines.
</description> 
    <dc:creator>sakina</dc:creator> 
    <pubDate>Wed, 08 Jun 2016 18:57:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3507</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3511/Information-Driven-Design.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3511</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3511&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Information Driven Design</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3511/Information-Driven-Design.aspx</link> 
    <description>It appears to me people still have trouble defining information requirements and, as such, they are at a loss as to how to build total systems. Thereby, they are content building either a single business process or a program. Therefore, here is the conceptual foundation for all system design.  Information Driven Design begins with a simple concept...</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 20 Apr 2016 20:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3511</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3472/Nobody-Thinks-Big-Anymore.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3472</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3472&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Nobody Thinks Big Anymore</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3472/Nobody-Thinks-Big-Anymore.aspx</link> 
    <description>While others are moving forward introducing new banking products, the Americans find themselves in the role of constantly fighting fires. You cannot move forward until you put your house in order by bringing standard practices and discipline into your work effort. This is what happens when you treat system design as an art form, as opposed to a science.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 25 Feb 2016 10:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3472</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3361/Design-Thinking-for-Business-Analysts.aspx#Comments</comments> 
    <slash:comments>4</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3361</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3361&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Design Thinking for Business Analysts</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3361/Design-Thinking-for-Business-Analysts.aspx</link> 
    <description>This article extends design thinking into a process and method that uses a range of common Business Analysis techniques to drive engagement through collaboration. It provides more structure to either side of the creative process to one better frame the domain of concern, and secondly after creativity has produced ideas, to prototype, refine, test and learn. The article also positions this process as a better way to arrive at a business case or pre-project phase, since it provides enormous insights through an engaging discovery process; something that would never occur within a traditional environment into investigation investment feasibility.</description> 
    <dc:creator>pomifritz</dc:creator> 
    <pubDate>Sun, 11 Oct 2015 18:59:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3361</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3354/Managing-Complexity.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3354</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3354&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Managing Complexity</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3354/Managing-Complexity.aspx</link> 
    <description>In a recent Information Technology discussion group I am involved with, someone posed the question,&amp;nbsp;&quot;What is complexity?&quot;&amp;nbsp;I was surprised by the question as I thought it was understood what complexity was all about. Evidently not. The person posing the question was primarily concerned with complexity in system design...</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 30 Sep 2015 20:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3354</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3318/The-USDAs-System-Snafu.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3318</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3318&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The USDA&#39;s System Snafu</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3318/The-USDAs-System-Snafu.aspx</link> 
    <description>&amp;nbsp;They took a software approach for designing MIDAS as opposed to a system approach. For example, they probably created a data base quickly, then tried to figure how to get data in and out of it. I would suspect the program source code was well written, probably using &quot;Agile&quot; techniques, but the fact remains none of it was designed to work in a concerted manner.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 23 Jul 2015 11:16:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3318</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3238/Process-Templates.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3238</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3238&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Process Templates</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3238/Process-Templates.aspx</link> 
    <description>Based on requirements, ASE decomposes a system into its sub-systems (business processes), the procedural work flow for each, and determine what programs are necessary to implement the computer procedures (software specs). To do this, we determined there were three basic types of sub-systems...</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Mon, 20 Apr 2015 02:50:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3238</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3214/Methodology-Design-101.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3214</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3214&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Methodology Design 101</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3214/Methodology-Design-101.aspx</link> 
    <description>...the fact remains, you cannot build anything of substance, be it a system or otherwise, without a methodology. The question then becomes, how to construct a methodology suitable for your company or a given project. To this end, I offer this tutorial on designing methodologies.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Fri, 13 Mar 2015 10:54:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3214</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3179/The-RIGHT-andWRONG-of-Design.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3179</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3179&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The &quot;RIGHT&quot; and&quot;WRONG&quot; of Design</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3179/The-RIGHT-andWRONG-of-Design.aspx</link> 
    <description>People ask me why I seem to be &amp;ldquo;black and white&amp;rdquo; on so many issues. Two reasons come to mind: first, I learned early in school that you do not get credit for making a mistake. If this has changed, please let me know. Second, the nature of my work in the information systems world has taught me there are right ways of doing things, as well as wrong ways. I am also not embarrassed to admit, &amp;ldquo;I do not know,&amp;rdquo; when I am unsure of myself, and will endeavor to find the answer. Failure to admit this is a sign of weakness, as is fabricating an excuse or leading someone down the wrong path.

In the many industries I have consulted with, I have learned there are right ways and wrong ways for conducting business:

* In manufacturing, there are defined methodologies for assembling just about any type of product, be it electronics, automobiles, ships, jet engines, or jets themselves. If the manufacturing sequence is not performed correctly, quality will suffer and defects will likely ensue.

* In the restaurant business, there are defined methodologies for cooking and customer service. If the cook mixes up the sequence of the recipe, believe me, you won&amp;rsquo;t want to eat it.

* The construction industry is no different. Regardless of what you are building, there is a defined sequence of tasks. As a hint, when you are building a house, it is generally a good idea to lay the foundation before you start constructing the roof.

* In information systems, you better have a clear understanding of the information requirements before designing the business processes, data base, work flows, and software. Unfortunately, most systems projects are doomed from the outset as they skip over requirements and begin to program almost immediately.

The lesson here is simple; if you perform the wrong task at the wrong time in a methodology, you are doomed. As any craftsman can tell you, it is not so much about the tools you use as it is about the methodology. Skipping steps represents a calculated risk to the success of a project. Believe it or not, people in the systems field fail to comprehend this simple concept. They are convinced specifying requirements and performing the steps for design is a colossal waste of time, with the the real work being in programming. This is like suggesting we build a bridge without first studying the problem and laying out the architectural plans; that the builders should show up at the job site and begin hammering and cutting the pieces of the bridge together without a set of blueprints. Let&amp;rsquo;s face it, if we built bridges in the same manner as we build systems in this country, this would be a nation run by ferryboats.

There is a science to building just about anything, be it a skyscraper, a bridge, an automobile, or an information system. It is all based on proven principles of design, it is hardly an artistic endeavor. This is not to suggest design is void of creativity; hardly, but a science is teachable and does not rely on a person&amp;rsquo;s intuition. Basically, it requires discipline which is something sorely lacking in the IT industry where people prefer &amp;ldquo;shooting from the hip&amp;rdquo; as opposed to learning the proper mechanics of a methodology.

As an aside, I have a friend in the art world who teaches illustration at a Midwest College. He too appreciates the need for methodology. As he adamantly instructs his students, it is not simply about starting to draw an illustration using paper and pencil, but the necessary steps for producing a proper graphic. So you see, even in the artwork there are &amp;ldquo;right&amp;rdquo; ways and &amp;ldquo;wrong&amp;rdquo; ways for doing something. It&amp;rsquo;s called a &amp;ldquo;methodology.&amp;rdquo;

Yes, it really is that &amp;ldquo;black and white.&amp;rdquo; Next question?

Keep the Faith!

Note: All trademarks both marked and unmarked belong to their respective companies.

Author: Tim Bryce is a writer and the Managing Director of M&amp;amp;JB Investment Company (M&amp;amp;JB) of Palm Harbor, Florida and has over 30 years of experience in the management consulting field. He can be reached at timb001@phmainstreet.com

For Tim&amp;rsquo;s columns, see:  timbryce.com

Copyright &amp;copy; 2015 by Tim Bryce. All rights reserved.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 29 Jan 2015 10:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3179</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2495/The-3-Amigos--BA-QA-and-Developer.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2495</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2495&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The 3 Amigos - BA, QA and Developer</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2495/The-3-Amigos--BA-QA-and-Developer.aspx</link> 
    <description>The 3 Amigos (sometimes referred to as a &amp;ldquo;Specification Workshop&amp;rdquo;) is a meeting where the Business Analyst presents requirements and test scenarios (collectively called a &amp;ldquo;feature&amp;rdquo;) for review by a member of the development team and a member of the quality assurance team.</description> 
    <dc:creator>ryanhewitt</dc:creator> 
    <pubDate>Wed, 17 Dec 2014 19:29:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2495</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1252/Complete-Business-Systems-Analysis-Model-UML-Example.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1252</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1252&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Complete Business-Systems Analysis Model (UML Example)</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1252/Complete-Business-Systems-Analysis-Model-UML-Example.aspx</link> 
    <description>This is a complete example of a Business/Systems Analysis Model using UML and including: Use Cases, Activity Diagrams, Context Diagram, and more.</description> 
    <dc:creator>baldrick</dc:creator> 
    <pubDate>Thu, 21 Aug 2014 13:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1252</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2990/Logical-Systems.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2990</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2990&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Logical Systems</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2990/Logical-Systems.aspx</link> 
    <description>I have had business friends over the years ask me why it seems so difficult and time consuming to upgrade their corporate systems to take advantage of the latest computer technology. In their minds, their systems are relatively simple; the concepts of such things as accounts receivable, accounts payable, inventory, manufacturing, etc. are relatively straight forward. Yet, companies incur millions of dollars in keeping them up-to-date. The question is, &quot;Why?&quot;</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 19 Jun 2014 06:15:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2990</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2985/Creating-Universal-Systems.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2985</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2985&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Creating Universal Systems</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2985/Creating-Universal-Systems.aspx</link> 
    <description>In this day and age of &amp;ldquo;globalization&amp;rdquo; more and more Information Systems are crossing geographical boundaries. Because of this, serious consideration should be given to making systems universally applicable to any country. Some might consider this an impossible task, but it is actually easier than you might think. It just requires a little common sense and some planning.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 11 Jun 2014 02:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2985</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2693/Five-Easy-Lessons-for-System-Design.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2693</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2693&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Five Easy Lessons for System Design</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2693/Five-Easy-Lessons-for-System-Design.aspx</link> 
    <description>I never really understood the hubbub associated with system design. People tend to look upon it as a complicated process. Actually it&#39;s not, yet the corporate landscape is littered with disastrous system projects costing millions of dollars, all because developers overlooked some rather simple principles for design and focused on technology instead.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 07 Aug 2013 06:39:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2693</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2569/Understanding-the-Natural-System.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2569</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2569&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Understanding the Natural System</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2569/Understanding-the-Natural-System.aspx</link> 
    <description>Every now and then I encounter a programmer who adamantly contends you cannot have an information system without some form of computer support. Actually, we&#39;ve had such systems well before the advent of the computer.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 25 Apr 2013 06:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2569</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2294/NANW-There-is-life-outside-the-waterfall-agile-continuum.aspx#Comments</comments> 
    <slash:comments>6</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2294</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2294&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>NANW: There is life outside the waterfall – agile continuum</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2294/NANW-There-is-life-outside-the-waterfall-agile-continuum.aspx</link> 
    <description>A great approach under the right circumstances, agile is not a universal solution for successfully completing a software project. Some projects are simply not compatible with most agile practices. For such projects, NANW has been driving results in terms of project and rework costs, integration time, and improved quality as reported by customers.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 12 Nov 2012 11:52:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2294</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2347/The-BAs-Journey--From-a-Current-to-a-Future-State.aspx#Comments</comments> 
    <slash:comments>3</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2347</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2347&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The BA&#39;s Journey - From a Current to a Future State</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2347/The-BAs-Journey--From-a-Current-to-a-Future-State.aspx</link> 
    <description>Many words have been written about the process of business analysis and how it can be performed on different types of projects. There are a multitude of tools and techniques which can be used plus methodologies and frameworks to suit a wide variety of circumstances. This makes it all too easy to get absorbed in the day-to-day detail and forget about the real purpose of business analysis – to fix a problem or provide the organisation with a new capability.</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Mon, 24 Sep 2012 08:07:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2347</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads%203/The_Business_Analyst_Journey_From_a_Current_to_a_Future_State.pdf" length="594805" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2273/An-Example-of-Choosing-a-Hybrid-SDLC-using-BPMN-and-the-Decision-Model.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2273</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2273&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>An Example of Choosing a Hybrid SDLC using BPMN and the Decision Model</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2273/An-Example-of-Choosing-a-Hybrid-SDLC-using-BPMN-and-the-Decision-Model.aspx</link> 
    <description>The purpose of this article is to provide project managers and business analysts an example of choosing a hybrid solution development life cycle (i.e., combination of agile and waterfall). Much discussion has transpired on the virtues of agile and waterfall approaches. &amp;#160;</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 30 Jul 2012 11:55:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2273</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2228/The-3-types-of-hybrid-projects-and-how-they-affect-the-business-analysts-work.aspx#Comments</comments> 
    <slash:comments>7</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2228</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2228&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The 3 types of hybrid projects, and how they affect the business analyst’s work</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2228/The-3-types-of-hybrid-projects-and-how-they-affect-the-business-analysts-work.aspx</link> 
    <description>I’ve written in the past about why hybrid approaches that incorporate traditional and agile methods of software development are been applied by organizations seeking to improve the results of their software projects. Here I’ll describe the 3 types of hybrid projects I have identified while working with different organizations in consulting assignments, and what impact each type has in the work of a business analyst.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 07 May 2012 04:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2228</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2133/Book-Review-Building-Business-Capability-by-Ron-Ross-and-Gladys-Lam.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2133</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2133&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Book Review: Building Business Capability by Ron Ross and Gladys Lam</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2133/Book-Review-Building-Business-Capability-by-Ron-Ross-and-Gladys-Lam.aspx</link> 
    <description>Ron Ross and Gladys Lam have written an important book for the business analyst community. It aims to get business analysts out of the technology ghetto that many of us get stuck in. Regardless of the type of analyst you are, I think it would be worth your time to get your hands on and read this book. I’ll explain why below.</description> 
    <dc:creator>craigwbrown</dc:creator> 
    <pubDate>Thu, 08 Mar 2012 11:15:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2133</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2139/3-misconceptions-I-would-like-to-see-removed-from-the-Agile-Extension-to-the-BABOK.aspx#Comments</comments> 
    <slash:comments>31</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2139</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2139&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>3  misconceptions I would like to see removed from the Agile Extension to the BABOK&#174;</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2139/3-misconceptions-I-would-like-to-see-removed-from-the-Agile-Extension-to-the-BABOK.aspx</link> 
    <description>The Agile Extension to the BABOK&#174; describes “business analysis areas of knowledge, their associated activities and tasks, and the skills necessary to be effective in their execution within the framework of agile software development”.&amp;#160; Below are 3 misconceptions that, in my opinion, the current draft of the Agile Extension is helping perpetuate.
&amp;#160;</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Tue, 21 Feb 2012 03:09:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2139</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2134/Methodologies-The-Dance-of-the-Fairies.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2134</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2134&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Methodologies &amp; The Dance of the Fairies</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2134/Methodologies-The-Dance-of-the-Fairies.aspx</link> 
    <description>In a nutshell, a methodology represents a series of steps in a project specifying Who is to perform What, When, Where, Why, and How (aka, &quot;5W+H&quot;), from start to finish. Perhaps the best way to think of a methodology is as a roadmap or an assembly line where a product is developed over a series of work stations.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 26 Jan 2012 08:19:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2134</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2077/Lean-Six-Sigma-for-non-industrial-organizations.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2077</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2077&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Lean Six Sigma for non-industrial organizations</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2077/Lean-Six-Sigma-for-non-industrial-organizations.aspx</link> 
    <description>Lean techniques use a process-oriented approach. In non-industrial organizations however, the process is invisible. In order to apply Lean techniques successfully in this environment, the visibility of processes has to be significantly increased. Employees have to learn to look at their organization from a process viewpoint. Furthermore, it is important that the method is applied to all layers of the organization.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Thu, 08 Dec 2011 00:59:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2077</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2082/Agile-vs-Traditional--Part-III-Winning-Through-Integrative-Thinking.aspx#Comments</comments> 
    <slash:comments>8</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2082</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2082&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Agile vs. Traditional... - Part III: Winning Through Integrative Thinking</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2082/Agile-vs-Traditional--Part-III-Winning-Through-Integrative-Thinking.aspx</link> 
    <description>Instead of taking for granted that either you find a flavor of agile that will fit the needs of your organization, or you must completely dismiss the use of agile methods, a much more valuable approach is to determine, for each individual project, which agile concepts should be embraced or not.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 04 Dec 2011 23:49:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2082</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2023/Iterative-Analysis-and-the-Diminishing-Business-Strategy.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2023</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2023&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Iterative Analysis and the Diminishing Business Strategy</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2023/Iterative-Analysis-and-the-Diminishing-Business-Strategy.aspx</link> 
    <description>Many IT managers have chosen to execute long-term projects in an iterative approach rather than a single linear fashion. This approach is not necessarily agile as the methodology is still “waterfall”-based but rather a series of waterfall executions (or terraced).&amp;#160;This approach introduces new challenges for business analysts.</description> 
    <dc:creator>stevebixler</dc:creator> 
    <pubDate>Sun, 06 Nov 2011 17:58:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2023</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2043/Agile-vs-Traditional---Part-II-Methods-are-a-means-to-the-end-of-project-success-not-the-end-themselves.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2043</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2043&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Agile vs. Traditional...   - Part II: Methods are a means to the end of project success, not the end themselves</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2043/Agile-vs-Traditional---Part-II-Methods-are-a-means-to-the-end-of-project-success-not-the-end-themselves.aspx</link> 
    <description>By taking a closer look at how your company is developing software, and what is working for projects with different profiles, it&amp;rsquo;s possible to leverage winning strategies and hybrid approaches to make your software initiatives equally or more successful in the future.</description> 
    <dc:creator>prabhuva</dc:creator> 
    <pubDate>Sun, 30 Oct 2011 10:18:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2043</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1926/Understanding-and-Managing-Agile-Transitions.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1926</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1926&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Understanding and Managing Agile Transitions</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1926/Understanding-and-Managing-Agile-Transitions.aspx</link> 
    <description>Software development process is undergoing seismic shift from traditional waterfall software methodologies towards agile methodologies. Agile software development methodologies deliver high quality software products in rapid iterations with high flexibility and adaptability to changing conditions. This article discusses the dynamics of agile projects by comparing it with the SDLC project framework to help the IT leaders and organizations plan effectively for transitioning to Agile software development methodologies.</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 25 Jul 2011 10:46:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1926</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1552/Three-Types-of-Design-Effort.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1552</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1552&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Three Types of Design Effort</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1552/Three-Types-of-Design-Effort.aspx</link> 
    <description>In I.T., are we really spending too much time on &quot;maintenance&quot;?&amp;#160; Within any systems development organization, there are but three types of work effort: new systems development, maintenance, and modification/improvements. A mature development organization will spend approximately 5% of its time on new development, 10% on maintenance, and 85% of its time on modification/improvements.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Sat, 18 Sep 2010 16:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1552</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1153/The-Next-Wave-Valuable-Products-First-Process-Second.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1153</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1153&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Next Wave: Valuable Products First, Process Second</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1153/The-Next-Wave-Valuable-Products-First-Process-Second.aspx</link> 
    <description>I&#39;m hearing the word &quot;value&quot; a lot lately. This is partly because the economic downturn has us looking to get the most for our money. But that&#39;s not all. More and more managers, business analysts, programmers and testers are talking to me about value. They are concerned that their products provide value for their end users. Many of them express a kind of process or tool fatigue. They are tired of being told that using a particular process or toolset is the key to their success. To them, value is a more important concept.</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 06 Dec 2009 05:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1153</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1056/Information-Systems-Theory-101.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1056</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1056&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Information Systems Theory 101</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1056/Information-Systems-Theory-101.aspx</link> 
    <description>Systems work is not as hard as you might think. However, we have a tendency in this business to complicate things by changing the vocabulary of systems work and introducing convoluted concepts and techniques, all of which makes it difficult to produce systems in a consistent manner. Consequently, there is a tendency to reinvent the wheel with each systems development project. I believe I owe it to my predecessors and the industry overall to describe basic systems theory, so that people can find the common ground needed to communicate and work. Fortunately, there are only four easy, yet important, concepts to grasp which I will try to define as succinctly as possible.</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Thu, 20 Aug 2009 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1056</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/811/The-Agile-Business-Analyst-Eyes-for-Waste.aspx#Comments</comments> 
    <slash:comments>3</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=811</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=811&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Agile Business Analyst: Eyes for Waste</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/811/The-Agile-Business-Analyst-Eyes-for-Waste.aspx</link> 
    <description>As an agile analyst, you know how easy it is to get lost in a blizzard of project details. The way to keep focused is to remind yourself of the chief reason for using agile processes: to deliver business value for your organization. With that in mind, we&amp;rsquo;ll look at specific ways you can combine two approaches: agile and lean.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Wed, 04 Feb 2009 05:37:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:811</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/596/Integrating-and-Understanding-Standard-Business-Analysis-Methodologies-To-Develop-New-Technology-Hybrids.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=596</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=596&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Integrating and Understanding Standard Business Analysis Methodologies To Develop New Technology Hybrids</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/596/Integrating-and-Understanding-Standard-Business-Analysis-Methodologies-To-Develop-New-Technology-Hybrids.aspx</link> 
    <description>Across North America, businesses in all sectors are adopting standard development methodologies to turn out a higher quality of goods and services. The tried and true approaches that have yielded such great results for competitors are heralded as best practices. But here is the sad news: no one methodology fits all. In fact, different methodologies are appropriate in fitting diverse projects. Some projects are so unique, future-thinking Business Analysts (BAs) are finding that the adoption of new hybrid concepts is the only smart way to go in problem solving tomorrow&amp;rsquo;s projects.

The word &amp;lsquo;fresh&amp;rsquo; describes that feeling of turning over a new leaf when January 1 rolls around each year &amp;ndash; and the sentiment we as individuals strive to maintain all year long when we set New Year&amp;rsquo;s resolutions. Much in the same vein as these annual goals, BAs seeking an innovative means by which they can see their requirements come to fruition are increasingly interested in the study of the existing methods that are in place within the industry, as well as fresh methods established through modeling and fusion. 
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 09 Nov 2008 10:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:596</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/536/Agile-Business-Analysis-Interview-with-Scott-Ambler.aspx#Comments</comments> 
    <slash:comments>18</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=536</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=536&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Agile Business Analysis: Interview with Scott Ambler</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/536/Agile-Business-Analysis-Interview-with-Scott-Ambler.aspx</link> 
    <description>Whether you&amp;rsquo;ve never heard of Agile or you just finished your nth Agile project, you need to understand that Agile is here to stay! Are you, the Business Analyst, an extinct species in this new world? Is your career changing? Do you need new skills?

Agile guru and visionary Scott Ambler talked with Adrian Marchis, ModernAnalyst.com&amp;#39;s Publishing Editor,&amp;nbsp;and shared his vision on what&amp;rsquo;s next for Agile and his thoughts on the role of the business analyst in the Agile world. 
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 07 Sep 2008 18:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:536</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/537/How-to-Be-an-Agile-Business-Analyst.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=537</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=537&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How to Be an Agile Business Analyst</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/537/How-to-Be-an-Agile-Business-Analyst.aspx</link> 
    <description>As an analyst practitioner I took it upon myself to act as a proxy for the product owner &amp;ndash; which in a corporate environment came with the challenges of multiple stakeholders, the fact that you are not the product owner and thus don&amp;#39;t really have the final say, and a number of other challenges that typically stump people trying to move to agile.

My circumstances were unique in some ways. I had worked in the organisation for some time and had established good relationships with all the key stakeholders. They really did trust me with their requirements because, over time, I had learnt (and shown I had earned) their business.

I also maintained high bandwidth communications with the stakeholders throughout the project and kept them informed of what was happening and how the system was shaping up in the context of their business needs. And expectations were managed.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 07 Sep 2008 05:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:537</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/500/Volere-Requirements-Techniques-an-Overview.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=500</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=500&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Volere Requirements Techniques: an Overview</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/500/Volere-Requirements-Techniques-an-Overview.aspx</link> 
    <description>The Volere requirements techniques were developed to answer the need for a common language for discovering requirements and connecting them to solutions. The language needs to be understandable by business people, customers, business analysts, engineers, designers, suppliers, testers or anyone else whose input is needed. All of these people have different skills and, not surprisingly, different views of what is important. A language intended for all of these people must recognise the differences in peoples’ viewpoints and yet have a consistent way of communicating and tracing the 
relevant knowledge. This realisation that requirements is a socio-technical discipline has a strong influence on the development of the techniques.
Author: Suzanne Robertson &amp;amp; James Robertson, The Atlantic Systems Guild</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Thu, 24 Jul 2008 05:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:500</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/458/Current-Systems-Analysis.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=458</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=458&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Current Systems Analysis</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/458/Current-Systems-Analysis.aspx</link> 
    <description>The subject of current systems analysis is usually greeted with dismay or disdain by systems departments. There are many reasons for this. In many installations, the support of current systems takes more than 85% of the systems department&amp;#39;s time, and the departments are more than ready to get on with new systems development and bury the old, non-working systems as quickly as possible. In cases where systems do not require a lot of maintenance, the systems department may find that the current systems are not giving management the kind of information it needs for effective decision making; these current systems become likely candidates for replacement.

However, there are some very legitimate reasons for documenting existing systems...
</description> 
    <dc:creator>timbryce</dc:creator> 
    <pubDate>Wed, 18 Jun 2008 11:41:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:458</guid> 
    
</item>

    </channel>
</rss>